Integration of IXC CHA with IXC Provider
Introduction
The integration between IXC ACS and IXC Provider allows the two systems to communicate automatically, keeping data synchronized and reducing manual activities. With this active integration, device management becomes more centralized, reliable and efficient.
Through this link, information such as devices, status and association with customer logins are shared between platforms, supporting the automation of day-to-day operational tasks.
Establish a bidirectional communication between the IXC ACS and the IXC Provider for data synchronization and centralized control of devices.
Value delivery
The integration of the IXC ACS with the IXC Provider offers direct benefits to the operation:
Reduction of operating costs
Less need for manual actions
More efficient management of devices
Greater reliability of information
Automation of repetitive processes
Centralization of network monitoring
Step by step of integration: Integration is carried out in two main stages, involving configurations in the IXC Provider and the IXC ACS. ####### In the IXC Ombudsman
- Configure API ClientClique aqui para saber como configurar2. Copy information from Client ID and Client Secret
These data are available in the menu Integrations
They will be used to authenticate the IXC ACS in the IXC Provider
In the IXC ACS
Access Menu Tools > Systems integration and click New integration
Enable integration
Tell the URL of your IXC Provider**
In field Client ID, paste the value copied from the IXC Provider
In the field Client Secret, paste the corresponding value and click Save
After saving, click Synchronize to start data exchange between systems
I'll be right there # How Synchronisation Works
The synchronization process follows some important rules:
What? When synchronization is performed by IXC ACS, the system consults the IXC Provider and receives only devices that have linked and active login.
What? When a new deviceis added to the ACS, your data is sent to the IXC Provider. If possible, the Provider returns thelogin linked** to that device.
What? When a device is manually deleted from the ACS**, the ACS sends a webhook to the IXC Provider so that the device is also removed from integration on their side. In this case, the device is no longer accounted for in the integration into both systems.
What? When the mass exclusion of devices occurs in ACS**, according to the criteria defined inconfigurações do servidor,the integration data of these devices are removed only in ACS. In this situation,no webhook is sent to the IXC Provider. The removal of devices on the Provider's side** does not happen automaticallyand will only be performed when the provider itself executes the synchronization process**.
What? The IXC ACS performs an automatic synchronization routine daily at dawn**, validating updated devices or new devices that have linked login. This routine has the same behavior as manual synchronization.
Integration check
To check that integration is working properly:
What? Access integration in the IXC ACS and click Synchronize
What? Return will only indicate devices with active and linked login in the IXC Provider
Differences in device numbers between systems can occur as explained in the synchronization rules.
I'll be right there # Integration-enabled features
With active integration, the following resources are available:
Automatic synchronization of devices between IXC ACS and IXC Provider
Bidirectional communication between systems
Use of speedtest with contracted plan information
- When performing a speedtest, the ACS consults the IXC Provider and displays the contracted band of the customer, allowing to compare with the speed delivered.
- Device Search
It is possible to perform the device search using the CPF, the social reason or the customer's phone, provided that this data is linked to the device in the IXC Provider**.
Common questions:
Why is the number of synchronized devices different between the ACS and the IXC Provider?
This can happen when:
- Devices were manually excluded from ACS
- The routine of mass exclusion in the ACS was performed and synchronization has not yet run in the IXC Provider
- There are devices without linked login
[!quote]- Why is integration not working or showing error while synchronizing?
Some common causes:
- Client ID, Client Secret or incorrect public key or with additional spaces
- IXC URL incorrectly informed Provider
- Network problems between systems
If the error persists, it is recommended to activate the support for validation.
Final considerations
Integration between the IXC ACS and the IXC Provider is essential for more efficient and automated network management. When configured correctly, it reduces manual errors, improves the visibility of the devices and ensures greater operational reliability. Maintaining revised settings and monitoring synchronisation helps ensure that integration continues to meet the provider's needs.
